Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4248770f227df32063c359936dd34f5dad46e0167c9683bdd2a7e8e1958bcab1

Tx prefix hash: 0d1c51208fd0a3b5f3c36bc51ab6c222a8ea4cdfdc2da3eb78e7799c06137b70
Tx public key: 5e9cbc598e2a8fc2b6085275f5dc6fa4c1c97bc4337903f5e4be68ff5fd383d0
Timestamp: 1672977824 Timestamp [UCT]: 2023-01-06 04:03:44 Age [y:d:h:m:s]: 01:331:04:47:51
Block: 668583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497727 RingCT/type: yes/0
Extra: 015e9cbc598e2a8fc2b6085275f5dc6fa4c1c97bc4337903f5e4be68ff5fd383d002110000000152542ceb000000000000000000

1 output(s) for total of 3.738582238000 dcy

stealth address amount amount idx
00: 1b806ef945386a5e7df40d3b2d7d6a321107eaa0ce474c75c1bb35124f28c7b7 3.738582238000 1109838 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 668593, "vin": [ { "gen": { "height": 668583 } } ], "vout": [ { "amount": 3738582238, "target": { "key": "1b806ef945386a5e7df40d3b2d7d6a321107eaa0ce474c75c1bb35124f28c7b7" } } ], "extra": [ 1, 94, 156, 188, 89, 142, 42, 143, 194, 182, 8, 82, 117, 245, 220, 111, 164, 193, 201, 123, 196, 51, 121, 3, 245, 228, 190, 104, 255, 95, 211, 131, 208, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8