Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eefd6dd7007d8c0bc6cf03ea68859552db33565057a13de5b40c3206cc4d5281

Tx prefix hash: 53a50e2dc4e26cca6f812cd50b3f4d8a129f2d64053506e299f72e4bdcc75e67
Tx public key: eeb048ea5265bf69850f5ee938a5f6093ef3ed9fefe14bb174e7f91ff26c5603
Timestamp: 1726077121 Timestamp [UCT]: 2024-09-11 17:52:01 Age [y:d:h:m:s]: 00:117:16:55:07
Block: 1107935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84176 RingCT/type: yes/0
Extra: 01eeb048ea5265bf69850f5ee938a5f6093ef3ed9fefe14bb174e7f91ff26c560302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17fb8500b87932feba6f1d9b0bbf831bdf7cd4bd433e6c5b3916dc24f71e54c8 0.600000000000 1585654 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": 1107945, "vin": [ { "gen": { "height": 1107935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17fb8500b87932feba6f1d9b0bbf831bdf7cd4bd433e6c5b3916dc24f71e54c8" } } ], "extra": [ 1, 238, 176, 72, 234, 82, 101, 191, 105, 133, 15, 94, 233, 56, 165, 246, 9, 62, 243, 237, 159, 239, 225, 75, 177, 116, 231, 249, 31, 242, 108, 86, 3, 2, 17, 0, 0, 0, 2, 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