Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27c532fe9389fc5da3a9613d7b0db5032e874c09b5bd9287c7f3e221c0ebad52

Tx prefix hash: 267397f15992d0e2adbab7bb8b632f0b76364a35d7aa308ddf98d3941003654c
Tx public key: 762bd0f3bf43fe9c3ff392d427f89560179a535ec78ff3143e4211e0ccdf1847
Timestamp: 1741328764 Timestamp [UCT]: 2025-03-07 06:26:04 Age [y:d:h:m:s]: 00:257:19:47:08
Block: 1233924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182013 RingCT/type: yes/0
Extra: 01762bd0f3bf43fe9c3ff392d427f89560179a535ec78ff3143e4211e0ccdf18470211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efc0e0b3ce8e0f3258840e077d85efcdfb034a677b4ed803bf5f2c630e0093c4 0.600000000000 1720849 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": 1233934, "vin": [ { "gen": { "height": 1233924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efc0e0b3ce8e0f3258840e077d85efcdfb034a677b4ed803bf5f2c630e0093c4" } } ], "extra": [ 1, 118, 43, 208, 243, 191, 67, 254, 156, 63, 243, 146, 212, 39, 248, 149, 96, 23, 154, 83, 94, 199, 143, 243, 20, 62, 66, 17, 224, 204, 223, 24, 71, 2, 17, 0, 0, 0, 3, 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