Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2fb2af7f6daf2f3b92999a09fa3101d67c28841b84e32bd7b504e485aa366f6

Tx prefix hash: bec260f7c768e55a2b30455d6517e6252d241454c890eb6997c1db42c43aea78
Tx public key: e56de5c3c8ff782635c179cedfbe9b955bbbcfc057d7ec26f1ede283cc617e3e
Timestamp: 1718725726 Timestamp [UCT]: 2024-06-18 15:48:46 Age [y:d:h:m:s]: 00:277:03:02:43
Block: 1046986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198036 RingCT/type: yes/0
Extra: 01e56de5c3c8ff782635c179cedfbe9b955bbbcfc057d7ec26f1ede283cc617e3e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f27ab78b19497b9ee1fd754fab11e9eeb72c1f7f6b3e0ab9119513f23d1b0664 0.600000000000 1516805 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": 1046996, "vin": [ { "gen": { "height": 1046986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f27ab78b19497b9ee1fd754fab11e9eeb72c1f7f6b3e0ab9119513f23d1b0664" } } ], "extra": [ 1, 229, 109, 229, 195, 200, 255, 120, 38, 53, 193, 121, 206, 223, 190, 155, 149, 91, 187, 207, 192, 87, 215, 236, 38, 241, 237, 226, 131, 204, 97, 126, 62, 2, 17, 0, 0, 0, 3, 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