Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ad72cf20e63b10aecbe5a9099898af05e1e920cc9500ea65498a09a118378fc

Tx prefix hash: 90650fea9e709900364a5e4d8b008ab47d12f15c3f18cde7b5dabbe41f0ec9c2
Tx public key: 4030e00b83ce30b4dc1c6f26a19dcd82f3c66f90234ad4fdc70cbd96a27b5083
Timestamp: 1717510948 Timestamp [UCT]: 2024-06-04 14:22:28 Age [y:d:h:m:s]: 01:007:12:52:10
Block: 1036931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266249 RingCT/type: yes/0
Extra: 014030e00b83ce30b4dc1c6f26a19dcd82f3c66f90234ad4fdc70cbd96a27b50830211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea4d8db13c6224d798df0710bd374d92572fae41bc232f38ae62ed46d9d45b26 0.600000000000 1505462 of 15

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": 1036941, "vin": [ { "gen": { "height": 1036931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea4d8db13c6224d798df0710bd374d92572fae41bc232f38ae62ed46d9d45b26" } } ], "extra": [ 1, 64, 48, 224, 11, 131, 206, 48, 180, 220, 28, 111, 38, 161, 157, 205, 130, 243, 198, 111, 144, 35, 74, 212, 253, 199, 12, 189, 150, 162, 123, 80, 131, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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