Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd69662db1f1fb66912d6ada6436670a47d5a11069907383f00f3343c1f1097f

Tx prefix hash: af1b1652ce2983012200b7ac8c7b76df524b34f441ba4b8d76c3fc6161cfc216
Tx public key: d251e075ad41e47eda626fda95e812942da50c34ea32a7f722eeb2c2de90eea3
Timestamp: 1746220083 Timestamp [UCT]: 2025-05-02 21:08:03 Age [y:d:h:m:s]: 00:203:03:18:38
Block: 1274408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142899 RingCT/type: yes/0
Extra: 01d251e075ad41e47eda626fda95e812942da50c34ea32a7f722eeb2c2de90eea30211000000091f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcdc3d01cfe96ff1ce8c5b5e1e4319677e5f6fa5cd350fb77b09ff17acdbd61b 0.600000000000 1761703 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": 1274418, "vin": [ { "gen": { "height": 1274408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcdc3d01cfe96ff1ce8c5b5e1e4319677e5f6fa5cd350fb77b09ff17acdbd61b" } } ], "extra": [ 1, 210, 81, 224, 117, 173, 65, 228, 126, 218, 98, 111, 218, 149, 232, 18, 148, 45, 165, 12, 52, 234, 50, 167, 247, 34, 238, 178, 194, 222, 144, 238, 163, 2, 17, 0, 0, 0, 9, 31, 144, 81, 122, 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