Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2320168db3433482d2fb69098bd5ef4a555104eaf6273b3b86c4e3dff9888ac5

Tx prefix hash: 640f96ad0b057a98689db76d9066e959f8d9ca5b30b2aa4d5bb88dfcf4b0a0bf
Tx public key: bd670ded6a818a2501739e92d2725139449ecc1bb2e057df1d6961df706299bb
Timestamp: 1630042484 Timestamp [UCT]: 2021-08-27 05:34:44 Age [y:d:h:m:s]: 03:233:17:14:03
Block: 321636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 941375 RingCT/type: yes/0
Extra: 01bd670ded6a818a2501739e92d2725139449ecc1bb2e057df1d6961df706299bb02110000001606faf294000000000000000000

1 output(s) for total of 52.758743830000 dcy

stealth address amount amount idx
00: f4227304861167e86e69ab979827521562e01a5eb7863e5a16d04872d9171c4a 52.758743830000 667631 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": 321646, "vin": [ { "gen": { "height": 321636 } } ], "vout": [ { "amount": 52758743830, "target": { "key": "f4227304861167e86e69ab979827521562e01a5eb7863e5a16d04872d9171c4a" } } ], "extra": [ 1, 189, 103, 13, 237, 106, 129, 138, 37, 1, 115, 158, 146, 210, 114, 81, 57, 68, 158, 204, 27, 178, 224, 87, 223, 29, 105, 97, 223, 112, 98, 153, 187, 2, 17, 0, 0, 0, 22, 6, 250, 242, 148, 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