Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2b1d11d9f6762e771ae13a710039158e71afc7a9d3586b8d102303d39eeeebe

Tx prefix hash: 0e737116aa1c26baad49c3c3b6accf8476887c78958525d8ef83969d7923ffdf
Tx public key: c8f15a66d5a6c0fb1ec9d134f1f3e36502a1d085f7a37e41c494538bac047159
Timestamp: 1738443857 Timestamp [UCT]: 2025-02-01 21:04:17 Age [y:d:h:m:s]: 00:336:02:05:12
Block: 1210028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238045 RingCT/type: yes/0
Extra: 01c8f15a66d5a6c0fb1ec9d134f1f3e36502a1d085f7a37e41c494538bac04715902110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1383c6969ec4f387f2f3fcb87312533756fc77714991769914fce8b57c2651f4 0.600000000000 1696775 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": 1210038, "vin": [ { "gen": { "height": 1210028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1383c6969ec4f387f2f3fcb87312533756fc77714991769914fce8b57c2651f4" } } ], "extra": [ 1, 200, 241, 90, 102, 213, 166, 192, 251, 30, 201, 209, 52, 241, 243, 227, 101, 2, 161, 208, 133, 247, 163, 126, 65, 196, 148, 83, 139, 172, 4, 113, 89, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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