Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12e73be12362c943e4320b080041814da5f99763fa1c30cb1b9607cbdd6cab54

Tx prefix hash: 9fc9a9e6736f72209b4a80b1e8d9401831583a97eb2d9272ad45cfcd05f50bca
Tx public key: c1cbe1f28f647d5d2dc9c032ff431989f11546684e5cfa2ae80183ab8111267f
Timestamp: 1737683384 Timestamp [UCT]: 2025-01-24 01:49:44 Age [y:d:h:m:s]: 00:145:22:40:32
Block: 1203964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104044 RingCT/type: yes/0
Extra: 01c1cbe1f28f647d5d2dc9c032ff431989f11546684e5cfa2ae80183ab8111267f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33c0b29c52d9742e4df02fa066701c0124c4aa6b61416a6e474ab71025efe473 0.600000000000 1690645 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": 1203974, "vin": [ { "gen": { "height": 1203964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33c0b29c52d9742e4df02fa066701c0124c4aa6b61416a6e474ab71025efe473" } } ], "extra": [ 1, 193, 203, 225, 242, 143, 100, 125, 93, 45, 201, 192, 50, 255, 67, 25, 137, 241, 21, 70, 104, 78, 92, 250, 42, 232, 1, 131, 171, 129, 17, 38, 127, 2, 17, 0, 0, 0, 5, 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