Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 215e56bc41148056a4b0ba059d51eca95094fda029b27b6d86862831512215d3

Tx prefix hash: d7447a490b2db8488ae6088a37bacf157c649e881aaeb5e012313bfb72228f3d
Tx public key: 648b14b70c37ce99d41dc16daa304fbe5411be22a39329409e1bd5d1aac69ad1
Timestamp: 1760932291 Timestamp [UCT]: 2025-10-20 03:51:31 Age [y:d:h:m:s]: 00:039:02:05:42
Block: 1393801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27974 RingCT/type: yes/0
Extra: 01648b14b70c37ce99d41dc16daa304fbe5411be22a39329409e1bd5d1aac69ad1021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 071c8cb5a3581fcf411a799e1d5e4950c9e0d20b4968e07c44f20fd5d7f55eae 0.600000000000 1882068 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": 1393811, "vin": [ { "gen": { "height": 1393801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "071c8cb5a3581fcf411a799e1d5e4950c9e0d20b4968e07c44f20fd5d7f55eae" } } ], "extra": [ 1, 100, 139, 20, 183, 12, 55, 206, 153, 212, 29, 193, 109, 170, 48, 79, 190, 84, 17, 190, 34, 163, 147, 41, 64, 158, 27, 213, 209, 170, 198, 154, 209, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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