Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 760f5da8f09a15964bb3104f7793ecfc80484fcc47c3ba3a51be0457c1f8021c

Tx prefix hash: a101abb72d1b0f04d3d19513f5d9ead16fa82bdb6ac9116f2f26dfc628389a6c
Tx public key: a95b3e40407ecc4069848fecaa0d834e01b06cf85e8b99b679fb8e842fda030d
Timestamp: 1703373588 Timestamp [UCT]: 2023-12-23 23:19:48 Age [y:d:h:m:s]: 01:142:08:11:25
Block: 919710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362884 RingCT/type: yes/0
Extra: 01a95b3e40407ecc4069848fecaa0d834e01b06cf85e8b99b679fb8e842fda030d02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fd604a3afd8d30cb71986891a041afd0518dcce63916ccde7c058d55bb4ba2b 0.600000000000 1377386 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": 919720, "vin": [ { "gen": { "height": 919710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fd604a3afd8d30cb71986891a041afd0518dcce63916ccde7c058d55bb4ba2b" } } ], "extra": [ 1, 169, 91, 62, 64, 64, 126, 204, 64, 105, 132, 143, 236, 170, 13, 131, 78, 1, 176, 108, 248, 94, 139, 153, 182, 121, 251, 142, 132, 47, 218, 3, 13, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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