Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0b6200e802c0b2792cee602eb550bec557984b12231025ac973eefc0994b149

Tx prefix hash: 6fdce47436087832f8a88bc0a3cf630196f17295d905b19b0ca5c25a1f022fe5
Tx public key: 2c216e7225b7ea0e37d2d7a385af3be8dcaacb02a419175775cfc5d8275c136f
Timestamp: 1709370679 Timestamp [UCT]: 2024-03-02 09:11:19 Age [y:d:h:m:s]: 01:037:14:25:10
Block: 969437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287871 RingCT/type: yes/0
Extra: 012c216e7225b7ea0e37d2d7a385af3be8dcaacb02a419175775cfc5d8275c136f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 583960e8a087ea4359de7a3262fbe01a46fe3465ec3fd07a510b4125955de24b 0.600000000000 1429268 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": 969447, "vin": [ { "gen": { "height": 969437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "583960e8a087ea4359de7a3262fbe01a46fe3465ec3fd07a510b4125955de24b" } } ], "extra": [ 1, 44, 33, 110, 114, 37, 183, 234, 14, 55, 210, 215, 163, 133, 175, 59, 232, 220, 170, 203, 2, 164, 25, 23, 87, 117, 207, 197, 216, 39, 92, 19, 111, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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