Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 131d2a1277c8b058563704a10e96dfc6b58647d799117561620e97a070f27cd8

Tx prefix hash: e14c12f13c25f771df058b7a340dceaddf049818fa8d093add0fd41bc31726b4
Tx public key: 826f8779fb603f3006ca5dfbd7dce5cf3bbf7b54e5e5c155a3436d5230e23da3
Timestamp: 1727553571 Timestamp [UCT]: 2024-09-28 19:59:31 Age [y:d:h:m:s]: 00:220:14:31:48
Block: 1120180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157489 RingCT/type: yes/0
Extra: 01826f8779fb603f3006ca5dfbd7dce5cf3bbf7b54e5e5c155a3436d5230e23da302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da42f3f5cb7b62fc5e24d385ee457a9090b9694871c509d3260fe869af64f3dc 0.600000000000 1602005 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": 1120190, "vin": [ { "gen": { "height": 1120180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da42f3f5cb7b62fc5e24d385ee457a9090b9694871c509d3260fe869af64f3dc" } } ], "extra": [ 1, 130, 111, 135, 121, 251, 96, 63, 48, 6, 202, 93, 251, 215, 220, 229, 207, 59, 191, 123, 84, 229, 229, 193, 85, 163, 67, 109, 82, 48, 226, 61, 163, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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