Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ad71bc3e53247ac0c3f6ec76bc0eff4bdd1e9b81edc515323d61478a1ddbc04

Tx prefix hash: 8035b5f8f5c33c3502dc1ff11dd9615bb16845a0ba0f7b1ec5a1401c00c3dfee
Tx public key: 6957eda7739676c8a5d67ac8bda8d8dd77eae2dcee0120a49ffb12257fcc4c42
Timestamp: 1723915467 Timestamp [UCT]: 2024-08-17 17:24:27 Age [y:d:h:m:s]: 01:168:11:45:37
Block: 1090021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378803 RingCT/type: yes/0
Extra: 016957eda7739676c8a5d67ac8bda8d8dd77eae2dcee0120a49ffb12257fcc4c4202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f69306794450fbc05738839ea9d41f130df606e81815bc8262ac565cb92fa47 0.600000000000 1564644 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": 1090031, "vin": [ { "gen": { "height": 1090021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f69306794450fbc05738839ea9d41f130df606e81815bc8262ac565cb92fa47" } } ], "extra": [ 1, 105, 87, 237, 167, 115, 150, 118, 200, 165, 214, 122, 200, 189, 168, 216, 221, 119, 234, 226, 220, 238, 1, 32, 164, 159, 251, 18, 37, 127, 204, 76, 66, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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