Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2c168165355f2dbcdc07a072041556f430c49b095e9c6ab2b055f6fb83fd69a

Tx prefix hash: 2a34e4e4d32c7317869c170fa3eb3bf7b54f1cba5c3977f18f8ac7c61bef059a
Tx public key: f6a5d5e5fa30650128d92ab124da9edef6cf6ecc91c9c77e3404fa2b222d59a3
Timestamp: 1577745516 Timestamp [UCT]: 2019-12-30 22:38:36 Age [y:d:h:m:s]: 05:155:00:32:03
Block: 35359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1260580 RingCT/type: yes/0
Extra: 01f6a5d5e5fa30650128d92ab124da9edef6cf6ecc91c9c77e3404fa2b222d59a30211000000088a2ee0d9000000000000000000

1 output(s) for total of 468.642649024000 dcy

stealth address amount amount idx
00: 0a346cb2e65e49577958a55f3a60b2e4fbca4effb91f9ef15b517acd4bbeaa66 468.642649024000 59581 of 0

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": 35369, "vin": [ { "gen": { "height": 35359 } } ], "vout": [ { "amount": 468642649024, "target": { "key": "0a346cb2e65e49577958a55f3a60b2e4fbca4effb91f9ef15b517acd4bbeaa66" } } ], "extra": [ 1, 246, 165, 213, 229, 250, 48, 101, 1, 40, 217, 42, 177, 36, 218, 158, 222, 246, 207, 110, 204, 145, 201, 199, 126, 52, 4, 250, 43, 34, 45, 89, 163, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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