Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 097f4da475d97124a767275d128cfe30130e7f990d2c26db63256755d9f2c766

Tx prefix hash: bc2044e08f8e7885335a6b50c8d7c157ac323ab11a8354c0cb6c0601c6e707da
Tx public key: 21e4a00dfb9c69297d4bddcef961f6d4e81141605346bdfc81c6d0309f4526ab
Timestamp: 1706267117 Timestamp [UCT]: 2024-01-26 11:05:17 Age [y:d:h:m:s]: 01:108:10:30:07
Block: 943674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338619 RingCT/type: yes/0
Extra: 0121e4a00dfb9c69297d4bddcef961f6d4e81141605346bdfc81c6d0309f4526ab02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18515c80f750ca900e7968156d306ac1d9e5f4556f0c1bab32136ef64f2bc59f 0.600000000000 1401882 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": 943684, "vin": [ { "gen": { "height": 943674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18515c80f750ca900e7968156d306ac1d9e5f4556f0c1bab32136ef64f2bc59f" } } ], "extra": [ 1, 33, 228, 160, 13, 251, 156, 105, 41, 125, 75, 221, 206, 249, 97, 246, 212, 232, 17, 65, 96, 83, 70, 189, 252, 129, 198, 208, 48, 159, 69, 38, 171, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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