Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a74c7d79ee5bf7590d1a402e3b61f9fc27bd8eef57a637b22f15e365da9c8aa2

Tx prefix hash: fb35d8ccac104ab27a9c9b7a4288ededc8231def78f9b5b69e5b0a03382c068d
Tx public key: d0daa1883762b5f38397dd7df8984729491cc68e585cf8af9baab66907a109d1
Timestamp: 1729394891 Timestamp [UCT]: 2024-10-20 03:28:11 Age [y:d:h:m:s]: 00:035:08:20:25
Block: 1135432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25227 RingCT/type: yes/0
Extra: 01d0daa1883762b5f38397dd7df8984729491cc68e585cf8af9baab66907a109d1021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc02d2f3adbd029f5bed5c35260cec69b5af6e1a686deff67aac3e8a5374d00c 0.600000000000 1618769 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": 1135442, "vin": [ { "gen": { "height": 1135432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc02d2f3adbd029f5bed5c35260cec69b5af6e1a686deff67aac3e8a5374d00c" } } ], "extra": [ 1, 208, 218, 161, 136, 55, 98, 181, 243, 131, 151, 221, 125, 248, 152, 71, 41, 73, 28, 198, 142, 88, 92, 248, 175, 155, 170, 182, 105, 7, 161, 9, 209, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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