Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47e01dc632f4ec557e4113db5ce291f9011e8b33253f4920ee5cbdb641799764

Tx prefix hash: bc234c56136719ed6ef9979cd20c11ef0e93d0e488a6bc49e2f113a7eba9c3d1
Tx public key: c0b5f1775d4d34d933a75643c52b115ddce5ec2b44b1436f4acf05ce70d52ea6
Timestamp: 1666453703 Timestamp [UCT]: 2022-10-22 15:48:23 Age [y:d:h:m:s]: 02:164:16:41:51
Block: 614639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639366 RingCT/type: yes/0
Extra: 01c0b5f1775d4d34d933a75643c52b115ddce5ec2b44b1436f4acf05ce70d52ea602110000000933af99f4000000000000000000

1 output(s) for total of 5.642166299000 dcy

stealth address amount amount idx
00: 80402513bc1b627f24909f865dbdf20976bb75b6d799c03160b16068cf678c4d 5.642166299000 1052036 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": 614649, "vin": [ { "gen": { "height": 614639 } } ], "vout": [ { "amount": 5642166299, "target": { "key": "80402513bc1b627f24909f865dbdf20976bb75b6d799c03160b16068cf678c4d" } } ], "extra": [ 1, 192, 181, 241, 119, 93, 77, 52, 217, 51, 167, 86, 67, 197, 43, 17, 93, 220, 229, 236, 43, 68, 177, 67, 111, 74, 207, 5, 206, 112, 213, 46, 166, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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