Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e94666abad798367f1e565ca5fc3bf51115f04d5b02e33a4ae331da23c2d4a0

Tx prefix hash: 607faad6f8e66578ba94c434a8dce5d5f368899dc1a67f0c0a8f6495310f4301
Tx public key: 6bf0c5d96bd5aaf1e4577bbaa29d33b0e0e1d4907e0f40e89d3578c1f7b864b4
Timestamp: 1693854683 Timestamp [UCT]: 2023-09-04 19:11:23 Age [y:d:h:m:s]: 01:212:16:09:28
Block: 840977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413111 RingCT/type: yes/0
Extra: 016bf0c5d96bd5aaf1e4577bbaa29d33b0e0e1d4907e0f40e89d3578c1f7b864b4021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.003446362000 dcy

stealth address amount amount idx
00: 111e3421e768509d22d2ace5d64dfecc6119a0842cccab35c9d5850adc1b8417 1.003446362000 1293965 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": 840987, "vin": [ { "gen": { "height": 840977 } } ], "vout": [ { "amount": 1003446362, "target": { "key": "111e3421e768509d22d2ace5d64dfecc6119a0842cccab35c9d5850adc1b8417" } } ], "extra": [ 1, 107, 240, 197, 217, 107, 213, 170, 241, 228, 87, 123, 186, 162, 157, 51, 176, 224, 225, 212, 144, 126, 15, 64, 232, 157, 53, 120, 193, 247, 184, 100, 180, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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