Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5ca6503dcdb7648f53415e245be0bd39ce05f62637fd3cd7e0018c89d078708

Tx prefix hash: 766285a602367cc6a484aa241bcd75d52e6976c188d34d1245a73d4e3576965f
Tx public key: c0fd28ed647ba28b26e857796389ff3f3b1a31712dc955d9845741cf6750faab
Timestamp: 1701486541 Timestamp [UCT]: 2023-12-02 03:09:01 Age [y:d:h:m:s]: 00:358:19:49:30
Block: 904060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256939 RingCT/type: yes/0
Extra: 01c0fd28ed647ba28b26e857796389ff3f3b1a31712dc955d9845741cf6750faab02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.620117381000 dcy

stealth address amount amount idx
00: 2093a8ca5bdfb87673777f6a4f961a47071abb8033d5c79d7cd9fdace8a77c37 0.620117381000 1360763 of 0

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": 904070, "vin": [ { "gen": { "height": 904060 } } ], "vout": [ { "amount": 620117381, "target": { "key": "2093a8ca5bdfb87673777f6a4f961a47071abb8033d5c79d7cd9fdace8a77c37" } } ], "extra": [ 1, 192, 253, 40, 237, 100, 123, 162, 139, 38, 232, 87, 121, 99, 137, 255, 63, 59, 26, 49, 113, 45, 201, 85, 217, 132, 87, 65, 207, 103, 80, 250, 171, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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