Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff1b9343a13b943dc1c5fb5af6388affe0a4f297d334ec23f1812fa4da9ca86b

Tx prefix hash: 4dacd4bb664a39c519a9a51bbc58a9a95727efcd448f815ee676f37c0d8b42ca
Tx public key: eaddeca8842ae2465dcfe35372f79daf53a0d1edcbc5f092419db5d265181c09
Timestamp: 1724035773 Timestamp [UCT]: 2024-08-19 02:49:33 Age [y:d:h:m:s]: 00:228:20:57:09
Block: 1091018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163440 RingCT/type: yes/0
Extra: 01eaddeca8842ae2465dcfe35372f79daf53a0d1edcbc5f092419db5d265181c09021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bebf7e0bd36e27c3dd8f08df7d1ee497a7245367074cc39bf2db4c671f9ad1fd 0.600000000000 1565643 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": 1091028, "vin": [ { "gen": { "height": 1091018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bebf7e0bd36e27c3dd8f08df7d1ee497a7245367074cc39bf2db4c671f9ad1fd" } } ], "extra": [ 1, 234, 221, 236, 168, 132, 42, 226, 70, 93, 207, 227, 83, 114, 247, 157, 175, 83, 160, 209, 237, 203, 197, 240, 146, 65, 157, 181, 210, 101, 24, 28, 9, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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