Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4c3a06aca23bf0c9d1f724ed40dcd40e287740a61d5f4cb8e9df115dddd31d1

Tx prefix hash: 096179036c38c3b413462d1eef60d2401677e7c113dbde0f6fd9d5f9bd14876c
Tx public key: a439cbd5e4e32645ec9215bffbf189fe5263221929b19c3a7e459d49f82e2e63
Timestamp: 1728974248 Timestamp [UCT]: 2024-10-15 06:37:28 Age [y:d:h:m:s]: 00:161:17:22:58
Block: 1131957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115350 RingCT/type: yes/0
Extra: 01a439cbd5e4e32645ec9215bffbf189fe5263221929b19c3a7e459d49f82e2e63021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5c85ead056bb1fe085b58df8414f9886012b06cd6f674597f9c32508898791f 0.600000000000 1614866 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": 1131967, "vin": [ { "gen": { "height": 1131957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5c85ead056bb1fe085b58df8414f9886012b06cd6f674597f9c32508898791f" } } ], "extra": [ 1, 164, 57, 203, 213, 228, 227, 38, 69, 236, 146, 21, 191, 251, 241, 137, 254, 82, 99, 34, 25, 41, 177, 156, 58, 126, 69, 157, 73, 248, 46, 46, 99, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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