Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7180d771f467cfcf16575644694316b3e0c15838d6c51b684e071e7e627fdce0

Tx prefix hash: 0756df9df3d55b9122ba4a374d2b98b80cf3f5e693ed1fb83ada4d86585bcc91
Tx public key: d50d1dc800d0d2993b728be4e6e9dbc96f846a4a4a7606eeeaa7ef2f80e647d0
Timestamp: 1719510392 Timestamp [UCT]: 2024-06-27 17:46:32 Age [y:d:h:m:s]: 00:338:04:47:38
Block: 1053493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241714 RingCT/type: yes/0
Extra: 01d50d1dc800d0d2993b728be4e6e9dbc96f846a4a4a7606eeeaa7ef2f80e647d00211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3aba104a3b5acb1c26b2b4b407010de5206f282a74a9c2386125206e3dbd07a 0.600000000000 1523840 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": 1053503, "vin": [ { "gen": { "height": 1053493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3aba104a3b5acb1c26b2b4b407010de5206f282a74a9c2386125206e3dbd07a" } } ], "extra": [ 1, 213, 13, 29, 200, 0, 208, 210, 153, 59, 114, 139, 228, 230, 233, 219, 201, 111, 132, 106, 74, 74, 118, 6, 238, 234, 167, 239, 47, 128, 230, 71, 208, 2, 17, 0, 0, 0, 2, 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