Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47cf3c19c8efa10957099afa5a1d7100c39edb1302964b16db62b0c0d8c32860

Tx prefix hash: bc124a3d741002a8a59104113ffc4595f3de5fa96079cc0ad70229164154e1e1
Tx public key: d57df7e90cacba1f3df8f7fb37da3c9d1ef1ac0e2d9b1fe38df59196f43cc3d8
Timestamp: 1702205513 Timestamp [UCT]: 2023-12-10 10:51:53 Age [y:d:h:m:s]: 01:041:00:49:47
Block: 910034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290649 RingCT/type: yes/0
Extra: 01d57df7e90cacba1f3df8f7fb37da3c9d1ef1ac0e2d9b1fe38df59196f43cc3d802110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9c3fa1c630b54e024f17e9ffa70080796eb2dd421abbd75ec4aceb6f812cfee 0.600000000000 1367175 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": 910044, "vin": [ { "gen": { "height": 910034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9c3fa1c630b54e024f17e9ffa70080796eb2dd421abbd75ec4aceb6f812cfee" } } ], "extra": [ 1, 213, 125, 247, 233, 12, 172, 186, 31, 61, 248, 247, 251, 55, 218, 60, 157, 30, 241, 172, 14, 45, 155, 31, 227, 141, 245, 145, 150, 244, 60, 195, 216, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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