Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ac852f51f3801ec5dcbe36d0dea82ca88c21e72b3964931b49786e267344daa

Tx prefix hash: 49243b7f54f1faea6d98749ac61fdb1aeb79ae08d163b8de5bb6163f8be321f7
Tx public key: 92ef0b186bf9ed5e8cbfe236f42d7460a23188dc93c9d0a2eb6152f45affc4d3
Timestamp: 1637256301 Timestamp [UCT]: 2021-11-18 17:25:01 Age [y:d:h:m:s]: 03:039:16:08:06
Block: 377111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 807087 RingCT/type: yes/0
Extra: 0192ef0b186bf9ed5e8cbfe236f42d7460a23188dc93c9d0a2eb6152f45affc4d3021100000075e50744d3000000000000000000

1 output(s) for total of 34.552751536000 dcy

stealth address amount amount idx
00: dfa1e488dc40a41b62004e18e421a1f4d606f0a562f69ef2f30f511b4df36d71 34.552751536000 762811 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": 377121, "vin": [ { "gen": { "height": 377111 } } ], "vout": [ { "amount": 34552751536, "target": { "key": "dfa1e488dc40a41b62004e18e421a1f4d606f0a562f69ef2f30f511b4df36d71" } } ], "extra": [ 1, 146, 239, 11, 24, 107, 249, 237, 94, 140, 191, 226, 54, 244, 45, 116, 96, 162, 49, 136, 220, 147, 201, 208, 162, 235, 97, 82, 244, 90, 255, 196, 211, 2, 17, 0, 0, 0, 117, 229, 7, 68, 211, 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