Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42610b6456ea0ce6e3a0cb61fd25a95f6f4ff67cf46fd45ea4545b15a99c42bd

Tx prefix hash: d26b30d4451520e5021b710401bc9ad5600803c024ffebb49b8eaf7f427143e0
Tx public key: e641ba6444b7ff6b3432a8c4ea4f29e48aad52a657d8f7b93115399b3831fb37
Timestamp: 1721586137 Timestamp [UCT]: 2024-07-21 18:22:17 Age [y:d:h:m:s]: 00:172:19:00:36
Block: 1070691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123642 RingCT/type: yes/0
Extra: 01e641ba6444b7ff6b3432a8c4ea4f29e48aad52a657d8f7b93115399b3831fb3702110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddedcb70d95efde515d871be681280803848de601fbf218f24b3bd31a4ff0a81 0.600000000000 1542632 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": 1070701, "vin": [ { "gen": { "height": 1070691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddedcb70d95efde515d871be681280803848de601fbf218f24b3bd31a4ff0a81" } } ], "extra": [ 1, 230, 65, 186, 100, 68, 183, 255, 107, 52, 50, 168, 196, 234, 79, 41, 228, 138, 173, 82, 166, 87, 216, 247, 185, 49, 21, 57, 155, 56, 49, 251, 55, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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