Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 111d0d7c140ecb44f3f6e2f642b9f8128d768a4b28995c7f9486cfb20456c33f

Tx prefix hash: 7ef73528d0956dae5164ec2cdeb0acc70f65251d67dd096f4c5f23b363702055
Tx public key: 9d713e70ff84e255a1390cc0f403abfd78be508ad5d67c45cde40742dce8fea3
Timestamp: 1728753598 Timestamp [UCT]: 2024-10-12 17:19:58 Age [y:d:h:m:s]: 00:161:16:08:23
Block: 1130124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115333 RingCT/type: yes/0
Extra: 019d713e70ff84e255a1390cc0f403abfd78be508ad5d67c45cde40742dce8fea302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc35306a3e703dc09ffd37346f4338d30423afb7adf34e79d9f10d12dd68e5ed 0.600000000000 1612997 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": 1130134, "vin": [ { "gen": { "height": 1130124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc35306a3e703dc09ffd37346f4338d30423afb7adf34e79d9f10d12dd68e5ed" } } ], "extra": [ 1, 157, 113, 62, 112, 255, 132, 226, 85, 161, 57, 12, 192, 244, 3, 171, 253, 120, 190, 80, 138, 213, 214, 124, 69, 205, 228, 7, 66, 220, 232, 254, 163, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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