Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f4cd9e78e61c2cf53a9a8725b1b39f6907b46c5c3e2e645e70536fa2e92e753

Tx prefix hash: 8f91058fe3d2a2f914c3a14c87741d6f3aefb44c8016a8cf9e266c7e74049671
Tx public key: d2fabfd15b22a24243e50918d01ac7ffd523a356f922d5515487c21b77c78981
Timestamp: 1721514409 Timestamp [UCT]: 2024-07-20 22:26:49 Age [y:d:h:m:s]: 01:109:14:36:58
Block: 1070109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336840 RingCT/type: yes/0
Extra: 01d2fabfd15b22a24243e50918d01ac7ffd523a356f922d5515487c21b77c7898102110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b634f8e7513f2cba391495aa540c647dc803f2d4f868e29c465974db9f0c90b2 0.600000000000 1541804 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": 1070119, "vin": [ { "gen": { "height": 1070109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b634f8e7513f2cba391495aa540c647dc803f2d4f868e29c465974db9f0c90b2" } } ], "extra": [ 1, 210, 250, 191, 209, 91, 34, 162, 66, 67, 229, 9, 24, 208, 26, 199, 255, 213, 35, 163, 86, 249, 34, 213, 81, 84, 135, 194, 27, 119, 199, 137, 129, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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