Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b25cfe291ac056d50f646e493fea0b28e6a88a6aeb0599532677c86ba78651fa

Tx prefix hash: 72380a86b9b30be5899acb54ea04813f164f4e619adda320a839ae2741ffe2e9
Tx public key: 1189ff7a2af6556f212b5bfd68c9031cfea98d0e405fb5200701d21f28c8588f
Timestamp: 1698103797 Timestamp [UCT]: 2023-10-23 23:29:57 Age [y:d:h:m:s]: 01:161:23:58:33
Block: 876232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376777 RingCT/type: yes/0
Extra: 011189ff7a2af6556f212b5bfd68c9031cfea98d0e405fb5200701d21f28c8588f021100000005faf35c9c000000000000000000

1 output(s) for total of 0.766795686000 dcy

stealth address amount amount idx
00: 05434ebe416391acee8820ccaa3ae149e5112dd0bcd6611056c1997e29d84f0d 0.766795686000 1331548 of 0

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": 876242, "vin": [ { "gen": { "height": 876232 } } ], "vout": [ { "amount": 766795686, "target": { "key": "05434ebe416391acee8820ccaa3ae149e5112dd0bcd6611056c1997e29d84f0d" } } ], "extra": [ 1, 17, 137, 255, 122, 42, 246, 85, 111, 33, 43, 91, 253, 104, 201, 3, 28, 254, 169, 141, 14, 64, 95, 181, 32, 7, 1, 210, 31, 40, 200, 88, 143, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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