Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ada34035535e8123b05d0e8672dd7732878f9e5010747c2687eb5732a93ff1e8

Tx prefix hash: f09d801886b5d2fa24b3fd6bdd7c9404025dda1a3b1110fa14658d71af93638d
Tx public key: a015d2cbc3baee9f14ef5a86d514c2e9eb1002b915735ae60566406b0d3d9937
Timestamp: 1705694852 Timestamp [UCT]: 2024-01-19 20:07:32 Age [y:d:h:m:s]: 01:294:23:05:25
Block: 938926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469640 RingCT/type: yes/0
Extra: 01a015d2cbc3baee9f14ef5a86d514c2e9eb1002b915735ae60566406b0d3d99370211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da3c6da9f22462dfa53a5aa7420d08ccc7adc32ca75bd1e11cf1795aedef0e6d 0.600000000000 1397008 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": 938936, "vin": [ { "gen": { "height": 938926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da3c6da9f22462dfa53a5aa7420d08ccc7adc32ca75bd1e11cf1795aedef0e6d" } } ], "extra": [ 1, 160, 21, 210, 203, 195, 186, 238, 159, 20, 239, 90, 134, 213, 20, 194, 233, 235, 16, 2, 185, 21, 115, 90, 230, 5, 102, 64, 107, 13, 61, 153, 55, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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