Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f537f824223b8a37ac30b463bfb6ff262aacb587467b7ae5474e9627e83200e

Tx prefix hash: b7e5a5d09438f9ed12f6584816a8de35c30e8f59e5573cb19ebd061d10b773a2
Tx public key: 8e7e222128c05449f3c03745317fddb80f09460e5669a094faf21b3bea3645e2
Timestamp: 1729237134 Timestamp [UCT]: 2024-10-18 07:38:54 Age [y:d:h:m:s]: 00:037:11:49:05
Block: 1134138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26762 RingCT/type: yes/0
Extra: 018e7e222128c05449f3c03745317fddb80f09460e5669a094faf21b3bea3645e20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae3dcdebc0618b49e2a974a35c5d6f20794827579476168d2fcd7b4924b535e0 0.600000000000 1617393 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": 1134148, "vin": [ { "gen": { "height": 1134138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae3dcdebc0618b49e2a974a35c5d6f20794827579476168d2fcd7b4924b535e0" } } ], "extra": [ 1, 142, 126, 34, 33, 40, 192, 84, 73, 243, 192, 55, 69, 49, 127, 221, 184, 15, 9, 70, 14, 86, 105, 160, 148, 250, 242, 27, 59, 234, 54, 69, 226, 2, 17, 0, 0, 0, 3, 31, 10, 83, 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