Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464f9e21c024c4dc4946f2475cd4ccf42d02a9e9f36605b18b06e8ed8dd8ed7b

Tx prefix hash: f2a816b9af37a9cf57cf5dfd731bd767b32d3961f0de5b8d4e54178c43c697d1
Tx public key: 8eee5f3f2149562d4af9e909232c2af193faf4b3eca868bba0715ac08aef73e4
Timestamp: 1676838355 Timestamp [UCT]: 2023-02-19 20:25:55 Age [y:d:h:m:s]: 01:268:13:33:08
Block: 700607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452844 RingCT/type: yes/0
Extra: 018eee5f3f2149562d4af9e909232c2af193faf4b3eca868bba0715ac08aef73e402110000000275e3f0e9000000000000000000

1 output(s) for total of 2.928182128000 dcy

stealth address amount amount idx
00: df5cfb10c1f04841e2f28bae8b4f5bd1a6ef6850f82f1884a25529507ac5188c 2.928182128000 1144054 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": 700617, "vin": [ { "gen": { "height": 700607 } } ], "vout": [ { "amount": 2928182128, "target": { "key": "df5cfb10c1f04841e2f28bae8b4f5bd1a6ef6850f82f1884a25529507ac5188c" } } ], "extra": [ 1, 142, 238, 95, 63, 33, 73, 86, 45, 74, 249, 233, 9, 35, 44, 42, 241, 147, 250, 244, 179, 236, 168, 104, 187, 160, 113, 90, 192, 138, 239, 115, 228, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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