Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2abd7400708b7b46f1f09778c9f4ed8aa78caf33eedad6deec2598a55fe5a70e

Tx prefix hash: c114e15633a751f24e89e886a43f3d9c1e6db013bd87f7a56fc9c19c5953dab5
Tx public key: b12c2dd13c95bb493837924d2236f3c7d719a3e78a59e905ed08c83437c84521
Timestamp: 1709267005 Timestamp [UCT]: 2024-03-01 04:23:25 Age [y:d:h:m:s]: 00:357:06:08:05
Block: 968580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255425 RingCT/type: yes/0
Extra: 01b12c2dd13c95bb493837924d2236f3c7d719a3e78a59e905ed08c83437c845210211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75434852ab18c439e89edb0cf5058507fa0e59f33fe56ef4a8b65a91c1eae771 0.600000000000 1428397 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": 968590, "vin": [ { "gen": { "height": 968580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75434852ab18c439e89edb0cf5058507fa0e59f33fe56ef4a8b65a91c1eae771" } } ], "extra": [ 1, 177, 44, 45, 209, 60, 149, 187, 73, 56, 55, 146, 77, 34, 54, 243, 199, 215, 25, 163, 231, 138, 89, 233, 5, 237, 8, 200, 52, 55, 200, 69, 33, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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