Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41404f0859621ceac7e2f71fa5895c71c9939d5731f2d0fc6007605d19e16dce

Tx prefix hash: 49be213ec75208e2b27929b8beb5e0df88a8d050a621abf583f68b9fbacdf837
Tx public key: 40f112c34fc887c8029cbd3a227c78e3c4b5dd1a086e048911bf0febe07c6aa7
Timestamp: 1717310334 Timestamp [UCT]: 2024-06-02 06:38:54 Age [y:d:h:m:s]: 00:294:23:21:40
Block: 1035264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210798 RingCT/type: yes/0
Extra: 0140f112c34fc887c8029cbd3a227c78e3c4b5dd1a086e048911bf0febe07c6aa70211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c65df38410165ef6651c78a808bde490aa8efe09ea15ca20d89d92eb468cda71 0.600000000000 1503785 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": 1035274, "vin": [ { "gen": { "height": 1035264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c65df38410165ef6651c78a808bde490aa8efe09ea15ca20d89d92eb468cda71" } } ], "extra": [ 1, 64, 241, 18, 195, 79, 200, 135, 200, 2, 156, 189, 58, 34, 124, 120, 227, 196, 181, 221, 26, 8, 110, 4, 137, 17, 191, 15, 235, 224, 124, 106, 167, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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