Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 071227e66fd96235092b723d72e860bd4bb06cc95b480b89f7a229d08e7b1479

Tx prefix hash: f635706d31bfb34050f752e98d06eede95d0f0d586e5e989e8b32d6e3e1ca061
Tx public key: e9efda125cfa11774c0b6097804af50e5cfdc2c6cca866a07a02f340e7328376
Timestamp: 1699358493 Timestamp [UCT]: 2023-11-07 12:01:33 Age [y:d:h:m:s]: 01:138:23:19:51
Block: 886431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360505 RingCT/type: yes/0
Extra: 01e9efda125cfa11774c0b6097804af50e5cfdc2c6cca866a07a02f340e732837602110000000775e3f0e9000000000000000000

1 output(s) for total of 0.709391737000 dcy

stealth address amount amount idx
00: 7a0270c40a53a2023a0a765ead4e4dbefea31f50c652b807ee819da754d8723e 0.709391737000 1342248 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": 886441, "vin": [ { "gen": { "height": 886431 } } ], "vout": [ { "amount": 709391737, "target": { "key": "7a0270c40a53a2023a0a765ead4e4dbefea31f50c652b807ee819da754d8723e" } } ], "extra": [ 1, 233, 239, 218, 18, 92, 250, 17, 119, 76, 11, 96, 151, 128, 74, 245, 14, 92, 253, 194, 198, 204, 168, 102, 160, 122, 2, 243, 64, 231, 50, 131, 118, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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