Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2aabbb8dac6d2c70890b910f177a0b8ef0044e3e5da91d1c5758d2c029690d7

Tx prefix hash: 170c100173af603bfa06e3459551810fb1907e76c817fb2fa35407d03f6bf3e1
Tx public key: 9d478a00bf274064f1cd73c60ec6e7de0ffcaa8849a9c86adde2a4fd2c9fe6ef
Timestamp: 1674955529 Timestamp [UCT]: 2023-01-29 01:25:29 Age [y:d:h:m:s]: 02:064:01:36:15
Block: 684988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 567407 RingCT/type: yes/0
Extra: 019d478a00bf274064f1cd73c60ec6e7de0ffcaa8849a9c86adde2a4fd2c9fe6ef0211000000025029cbac000000000000000000

1 output(s) for total of 3.298757110000 dcy

stealth address amount amount idx
00: 6987553203cf0bb6c0088fe18c114f7700be4e19270d324f4081d41fd8eb32de 3.298757110000 1127271 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": 684998, "vin": [ { "gen": { "height": 684988 } } ], "vout": [ { "amount": 3298757110, "target": { "key": "6987553203cf0bb6c0088fe18c114f7700be4e19270d324f4081d41fd8eb32de" } } ], "extra": [ 1, 157, 71, 138, 0, 191, 39, 64, 100, 241, 205, 115, 198, 14, 198, 231, 222, 15, 252, 170, 136, 73, 169, 200, 106, 221, 226, 164, 253, 44, 159, 230, 239, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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