Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b883bca6577e6bbcc3afd1d0556378816f1a39bce38d24ccfeffe07efbe9383

Tx prefix hash: b043517b06e20b810a4e98c0ecc5b5bda0a69438aca2160f009b1205b8b64672
Tx public key: a1dc47f28797c898fd2c4f827e180df03f6394676797f468f9f51145874f7a13
Timestamp: 1702706666 Timestamp [UCT]: 2023-12-16 06:04:26 Age [y:d:h:m:s]: 01:329:13:21:43
Block: 914181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494395 RingCT/type: yes/0
Extra: 01a1dc47f28797c898fd2c4f827e180df03f6394676797f468f9f51145874f7a13021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8854811f93081230a644cbef65784e118e750fe72b8c4d96eb59991b7a7ca80 0.600000000000 1371467 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": 914191, "vin": [ { "gen": { "height": 914181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8854811f93081230a644cbef65784e118e750fe72b8c4d96eb59991b7a7ca80" } } ], "extra": [ 1, 161, 220, 71, 242, 135, 151, 200, 152, 253, 44, 79, 130, 126, 24, 13, 240, 63, 99, 148, 103, 103, 151, 244, 104, 249, 245, 17, 69, 135, 79, 122, 19, 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