Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c40a7112ccfe4f75f5bfc4e7cb372c147b387a93ac566db8721fb96f43c6ec10

Tx prefix hash: c25e6e3960a2c0d4753abc21565561bea25c748d10bc1540be3198d510d8d453
Tx public key: 2704567807e078dd3d87e5a52daf7a85aac9f33f5b09320f22537a241c6a3d5c
Timestamp: 1725878074 Timestamp [UCT]: 2024-09-09 10:34:34 Age [y:d:h:m:s]: 00:166:10:05:12
Block: 1106295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118726 RingCT/type: yes/0
Extra: 012704567807e078dd3d87e5a52daf7a85aac9f33f5b09320f22537a241c6a3d5c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c02954af50a14a75984e2fe4b849f97d34c53830371dab89a7937c4d2cf12262 0.600000000000 1583894 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": 1106305, "vin": [ { "gen": { "height": 1106295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c02954af50a14a75984e2fe4b849f97d34c53830371dab89a7937c4d2cf12262" } } ], "extra": [ 1, 39, 4, 86, 120, 7, 224, 120, 221, 61, 135, 229, 165, 45, 175, 122, 133, 170, 201, 243, 63, 91, 9, 50, 15, 34, 83, 122, 36, 28, 106, 61, 92, 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