Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8acfe281709611a3936338e0bb03c422dab25ad329d6b7d2e591d9810a6b7433

Tx prefix hash: 70626c47b7ae3bbdc4669684192944bf2f96d2db6e5179902909922596a1999d
Tx public key: abe754508dfb9ee084f9a3e8fef22859fa7913aced0e04ab62005c9b40809d5d
Timestamp: 1699875442 Timestamp [UCT]: 2023-11-13 11:37:22 Age [y:d:h:m:s]: 01:142:09:25:56
Block: 890722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362936 RingCT/type: yes/0
Extra: 01abe754508dfb9ee084f9a3e8fef22859fa7913aced0e04ab62005c9b40809d5d021100000005faf35c9c000000000000000000

1 output(s) for total of 0.686543808000 dcy

stealth address amount amount idx
00: c99dce09e0b724650e957080da37b5c66d2a09c0c9331d7b324bbaebaf4780c5 0.686543808000 1346751 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": 890732, "vin": [ { "gen": { "height": 890722 } } ], "vout": [ { "amount": 686543808, "target": { "key": "c99dce09e0b724650e957080da37b5c66d2a09c0c9331d7b324bbaebaf4780c5" } } ], "extra": [ 1, 171, 231, 84, 80, 141, 251, 158, 224, 132, 249, 163, 232, 254, 242, 40, 89, 250, 121, 19, 172, 237, 14, 4, 171, 98, 0, 92, 155, 64, 128, 157, 93, 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