Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7439add83f05b7f7cdc53755626e3ae31b1501fc64f937b4367adaa4dc055d3e

Tx prefix hash: 9f4efb5a652e3889d089b5b145764af8d197767be00caf871a5d7345e75efa6b
Tx public key: 6f279dea52a8e3786f3e81fc820dc3d6c7f5cee695403ac0567d61d0facfec05
Timestamp: 1705624819 Timestamp [UCT]: 2024-01-19 00:40:19 Age [y:d:h:m:s]: 01:298:08:34:54
Block: 938361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472049 RingCT/type: yes/0
Extra: 016f279dea52a8e3786f3e81fc820dc3d6c7f5cee695403ac0567d61d0facfec0502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9220e568e3749577cb5849a4b3bf86697669785eb7278541c993d7f5c499cae 0.600000000000 1396431 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": 938371, "vin": [ { "gen": { "height": 938361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9220e568e3749577cb5849a4b3bf86697669785eb7278541c993d7f5c499cae" } } ], "extra": [ 1, 111, 39, 157, 234, 82, 168, 227, 120, 111, 62, 129, 252, 130, 13, 195, 214, 199, 245, 206, 230, 149, 64, 58, 192, 86, 125, 97, 208, 250, 207, 236, 5, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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