Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6afe58a3857db3bb884f95cc33a701d226663adfa65849a8e2f1ca6e5c956b04

Tx prefix hash: d747db95d18f37fc51c292d2c69a6546102628a3c73dbd5d3b45dc2d99c18ac6
Tx public key: df0e0aa38dcbe25457977876c401dd7dfeaf648555693e0d803a49f85def25d7
Timestamp: 1717450001 Timestamp [UCT]: 2024-06-03 21:26:41 Age [y:d:h:m:s]: 00:291:00:36:08
Block: 1036416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207984 RingCT/type: yes/0
Extra: 01df0e0aa38dcbe25457977876c401dd7dfeaf648555693e0d803a49f85def25d70211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbfb8089133b1800e0cf745fb68781d1de0d270845f48f3d55d3d753dda63ea5 0.600000000000 1504943 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": 1036426, "vin": [ { "gen": { "height": 1036416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbfb8089133b1800e0cf745fb68781d1de0d270845f48f3d55d3d753dda63ea5" } } ], "extra": [ 1, 223, 14, 10, 163, 141, 203, 226, 84, 87, 151, 120, 118, 196, 1, 221, 125, 254, 175, 100, 133, 85, 105, 62, 13, 128, 58, 73, 248, 93, 239, 37, 215, 2, 17, 0, 0, 0, 3, 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