Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7be29c4da58363bf6c4d80c2a50ba247e57b7ae9c6cec52a9b8ea3c6d61e6d2e

Tx prefix hash: 1803001909da00ba54465732f2977992df415c287f52544d56b5bf6e73df094e
Tx public key: a16867f2ad59339169578d5026eea774dc4ed524ccf2ed1e243d71e0dd1ac81b
Timestamp: 1710551002 Timestamp [UCT]: 2024-03-16 01:03:22 Age [y:d:h:m:s]: 01:029:04:43:30
Block: 979238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281856 RingCT/type: yes/0
Extra: 01a16867f2ad59339169578d5026eea774dc4ed524ccf2ed1e243d71e0dd1ac81b02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b544e1707f54f62c505d20a1f57b62747bde860f3ba434e2535c87370a84ec5 0.600000000000 1439271 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": 979248, "vin": [ { "gen": { "height": 979238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b544e1707f54f62c505d20a1f57b62747bde860f3ba434e2535c87370a84ec5" } } ], "extra": [ 1, 161, 104, 103, 242, 173, 89, 51, 145, 105, 87, 141, 80, 38, 238, 167, 116, 220, 78, 213, 36, 204, 242, 237, 30, 36, 61, 113, 224, 221, 26, 200, 27, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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