Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 208afb4e214a5c1fa51211d4ed9525fcb4da261d9125ae28309a678f544842b7

Tx prefix hash: 79ddca862cc08b2a68a03e8d9b05caa1af9a2e288e45aa067e2afa21a4922a5e
Tx public key: 1c02b8ef5ffc4f39e3140d959cfb74c39da7247f3da96cb7fe54b375c4c27d80
Timestamp: 1574103735 Timestamp [UCT]: 2019-11-18 19:02:15 Age [y:d:h:m:s]: 05:210:17:10:28
Block: 12070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1293449 RingCT/type: yes/0
Extra: 011c02b8ef5ffc4f39e3140d959cfb74c39da7247f3da96cb7fe54b375c4c27d8002110000000166a80d00000000000000000000

1 output(s) for total of 559.767871400000 dcy

stealth address amount amount idx
00: 4b0d002dcf7e0da57f14723a1be4664bcb6afe7eb44c6b40a707324eb6bdab55 559.767871400000 13157 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": 12080, "vin": [ { "gen": { "height": 12070 } } ], "vout": [ { "amount": 559767871400, "target": { "key": "4b0d002dcf7e0da57f14723a1be4664bcb6afe7eb44c6b40a707324eb6bdab55" } } ], "extra": [ 1, 28, 2, 184, 239, 95, 252, 79, 57, 227, 20, 13, 149, 156, 251, 116, 195, 157, 167, 36, 127, 61, 169, 108, 183, 254, 84, 179, 117, 196, 194, 125, 128, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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