Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89a0b3181592a3aa70f39f5bf5c6b66f806b7a3d423d244036ebfb25f97a93e0

Tx prefix hash: 04b54a99210dd3724d4f00c5fb49b70068954300f74d1daa3edcde4b895c08cd
Tx public key: bf408d74c4c6ad80848ff3ef345eadc5f8b248e8f058523850f22b222a9aa129
Timestamp: 1575885460 Timestamp [UCT]: 2019-12-09 09:57:40 Age [y:d:h:m:s]: 04:353:12:37:47
Block: 24088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137615 RingCT/type: yes/0
Extra: 01bf408d74c4c6ad80848ff3ef345eadc5f8b248e8f058523850f22b222a9aa12902110000000cad433a0b000000000000000000

1 output(s) for total of 510.725247477000 dcy

stealth address amount amount idx
00: d9767b579abd88a7b88e2af44848ee654c84e45ed8051f473b04ad449e1aa369 510.725247477000 39077 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": 24098, "vin": [ { "gen": { "height": 24088 } } ], "vout": [ { "amount": 510725247477, "target": { "key": "d9767b579abd88a7b88e2af44848ee654c84e45ed8051f473b04ad449e1aa369" } } ], "extra": [ 1, 191, 64, 141, 116, 196, 198, 173, 128, 132, 143, 243, 239, 52, 94, 173, 197, 248, 178, 72, 232, 240, 88, 82, 56, 80, 242, 43, 34, 42, 154, 161, 41, 2, 17, 0, 0, 0, 12, 173, 67, 58, 11, 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