Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0818a481b103efa80e3335fe95445baafb6ef8e4b7529ad4c6f245948966b27a

Tx prefix hash: 0bc8ee4108443aefa92663e26940f776aa22063a25628bce73fbdbb0095916e2
Tx public key: bb7d3068f9c55adcb32d3e738e4a0310481dd9c0de922f7cb302c966ffd2433b
Timestamp: 1736824504 Timestamp [UCT]: 2025-01-14 03:15:04 Age [y:d:h:m:s]: 00:311:14:04:42
Block: 1196894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220196 RingCT/type: yes/0
Extra: 01bb7d3068f9c55adcb32d3e738e4a0310481dd9c0de922f7cb302c966ffd2433b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 536731647df91ac3ae5df098e7bb1b645350d63a53c1a097436ed5ac46f19a3e 0.600000000000 1683499 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": 1196904, "vin": [ { "gen": { "height": 1196894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "536731647df91ac3ae5df098e7bb1b645350d63a53c1a097436ed5ac46f19a3e" } } ], "extra": [ 1, 187, 125, 48, 104, 249, 197, 90, 220, 179, 45, 62, 115, 142, 74, 3, 16, 72, 29, 217, 192, 222, 146, 47, 124, 179, 2, 201, 102, 255, 210, 67, 59, 2, 17, 0, 0, 0, 6, 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