Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb0146cff9f79db7f2af31b33030a626af900fb36cb4371e83bc30999d9e5857

Tx prefix hash: be272f92e0169f63960b78900096adbdbb54922607ae3e7a0a40d82dfabdd0b3
Tx public key: 39766c3923948be2a1cc1c1eee82133730e4548cf6ab0ad6af229fd9ff46b29c
Timestamp: 1733082040 Timestamp [UCT]: 2024-12-01 19:40:40 Age [y:d:h:m:s]: 00:103:20:13:48
Block: 1165920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74020 RingCT/type: yes/0
Extra: 0139766c3923948be2a1cc1c1eee82133730e4548cf6ab0ad6af229fd9ff46b29c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0ad9bb03d07c25efa95af6f7aa01f6ac2c2bcbdda579ee41b92c0e7c9b6c7ac 0.600000000000 1651595 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": 1165930, "vin": [ { "gen": { "height": 1165920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0ad9bb03d07c25efa95af6f7aa01f6ac2c2bcbdda579ee41b92c0e7c9b6c7ac" } } ], "extra": [ 1, 57, 118, 108, 57, 35, 148, 139, 226, 161, 204, 28, 30, 238, 130, 19, 55, 48, 228, 84, 140, 246, 171, 10, 214, 175, 34, 159, 217, 255, 70, 178, 156, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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