Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f611e30ceb8d97e3c5168d700bf0b7cb5ebfe3ae8fb50e7c99dc961e60dc3b1d

Tx prefix hash: 16efe24956797c963714645d4a34675aae50dcabb6cf8134d0f0d3bf674827e6
Tx public key: 1a8e1db6e57c3dd09f45e5798fbce0e751c10e118211cfc1d05757b42b2ae22b
Timestamp: 1731964604 Timestamp [UCT]: 2024-11-18 21:16:44 Age [y:d:h:m:s]: 01:049:13:23:42
Block: 1156646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293909 RingCT/type: yes/0
Extra: 011a8e1db6e57c3dd09f45e5798fbce0e751c10e118211cfc1d05757b42b2ae22b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd67868338f63852ba256c2598e0c79f0c9f9ea4da07a46ab18c6b71fc385025 0.600000000000 1642269 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": 1156656, "vin": [ { "gen": { "height": 1156646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd67868338f63852ba256c2598e0c79f0c9f9ea4da07a46ab18c6b71fc385025" } } ], "extra": [ 1, 26, 142, 29, 182, 229, 124, 61, 208, 159, 69, 229, 121, 143, 188, 224, 231, 81, 193, 14, 17, 130, 17, 207, 193, 208, 87, 87, 180, 43, 42, 226, 43, 2, 17, 0, 0, 0, 1, 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