Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05f23ba41bad643051276f2ce6870acfeb19098348055861f12747d6a3b28086

Tx prefix hash: 477c6cf3b39196cc4aca1c35311e1beddb4812b6f670e6a7845b21b6088f3083
Tx public key: 4f53c6e5f64571fe7a811a9e5a29db94e6ad26e2f810592b9f3ca607eb99703d
Timestamp: 1640812595 Timestamp [UCT]: 2021-12-29 21:16:35 Age [y:d:h:m:s]: 03:029:22:22:56
Block: 406289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 800147 RingCT/type: yes/0
Extra: 014f53c6e5f64571fe7a811a9e5a29db94e6ad26e2f810592b9f3ca607eb99703d02110000001658821d9c000000000000000000

1 output(s) for total of 27.656916856000 dcy

stealth address amount amount idx
00: 809a6d1e9dac4a1adfdc9f283fa93997dc43a162e150021e2ca24f59f2014e3f 27.656916856000 807089 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": 406299, "vin": [ { "gen": { "height": 406289 } } ], "vout": [ { "amount": 27656916856, "target": { "key": "809a6d1e9dac4a1adfdc9f283fa93997dc43a162e150021e2ca24f59f2014e3f" } } ], "extra": [ 1, 79, 83, 198, 229, 246, 69, 113, 254, 122, 129, 26, 158, 90, 41, 219, 148, 230, 173, 38, 226, 248, 16, 89, 43, 159, 60, 166, 7, 235, 153, 112, 61, 2, 17, 0, 0, 0, 22, 88, 130, 29, 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