Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ce084e74123235c4279757038dc81cf10d8cce00d64a6d670414adda6cbb2e8

Tx prefix hash: c2d8cac53617d47535c77e57e2acb7c09f5cf9c726bf0e318d9e16633ce4d03e
Tx public key: 0a967422e89ced7f042d8c7e6340c9763b04280a804d09e6139bb511fa2965f4
Timestamp: 1736169507 Timestamp [UCT]: 2025-01-06 13:18:27 Age [y:d:h:m:s]: 00:167:16:11:52
Block: 1191488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119449 RingCT/type: yes/0
Extra: 010a967422e89ced7f042d8c7e6340c9763b04280a804d09e6139bb511fa2965f4021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 129b44f0b7e51b7ccc8b37aeca1df1569eb83dd06140bda3082c1e099eff9b81 0.600000000000 1678027 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": 1191498, "vin": [ { "gen": { "height": 1191488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "129b44f0b7e51b7ccc8b37aeca1df1569eb83dd06140bda3082c1e099eff9b81" } } ], "extra": [ 1, 10, 150, 116, 34, 232, 156, 237, 127, 4, 45, 140, 126, 99, 64, 201, 118, 59, 4, 40, 10, 128, 77, 9, 230, 19, 155, 181, 17, 250, 41, 101, 244, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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