Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cdd852d067c9100752a4758091fe0a281717cee95954225f1ee1ca930dbeb76

Tx prefix hash: 9de0dee6f6d24ae2db522b2e27e4484a1fe62f197adec11bf2a1b66c879a7475
Tx public key: 112ed5231749796c28bb4d7baecf7aab58d18a236bfcd3a71857a2f7daab6c0c
Timestamp: 1671886271 Timestamp [UCT]: 2022-12-24 12:51:11 Age [y:d:h:m:s]: 02:027:04:15:19
Block: 659550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541297 RingCT/type: yes/0
Extra: 01112ed5231749796c28bb4d7baecf7aab58d18a236bfcd3a71857a2f7daab6c0c021100000002e6d27f9c000000000000000000

1 output(s) for total of 4.005318258000 dcy

stealth address amount amount idx
00: 5c0a0ec45f0cedb3b2f099f6be5c8e4e4616e271ce0beea02a50b6f89868f0a8 4.005318258000 1100257 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": 659560, "vin": [ { "gen": { "height": 659550 } } ], "vout": [ { "amount": 4005318258, "target": { "key": "5c0a0ec45f0cedb3b2f099f6be5c8e4e4616e271ce0beea02a50b6f89868f0a8" } } ], "extra": [ 1, 17, 46, 213, 35, 23, 73, 121, 108, 40, 187, 77, 123, 174, 207, 122, 171, 88, 209, 138, 35, 107, 252, 211, 167, 24, 87, 162, 247, 218, 171, 108, 12, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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