Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91eef73dfcdbcba8ec59802b4b6a39e62251ca7914fe2e7f32907a439b269a98

Tx prefix hash: 1798a6d634622d95dfb4e3d0b48357a60a22bb3671f9647eeee7d8232961390a
Tx public key: e621929c357688d36d171f5df99cb4e86b7e4a458d33756fbb22f2f23cd40bad
Timestamp: 1705764912 Timestamp [UCT]: 2024-01-20 15:35:12 Age [y:d:h:m:s]: 01:150:21:52:24
Block: 939513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368880 RingCT/type: yes/0
Extra: 01e621929c357688d36d171f5df99cb4e86b7e4a458d33756fbb22f2f23cd40bad02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bc8c99838ed4e32e2e1f2c5ddd5358fa51fe7416e6fa55534b95ccd4a867dd7 0.600000000000 1397621 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": 939523, "vin": [ { "gen": { "height": 939513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bc8c99838ed4e32e2e1f2c5ddd5358fa51fe7416e6fa55534b95ccd4a867dd7" } } ], "extra": [ 1, 230, 33, 146, 156, 53, 118, 136, 211, 109, 23, 31, 93, 249, 156, 180, 232, 107, 126, 74, 69, 141, 51, 117, 111, 187, 34, 242, 242, 60, 212, 11, 173, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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