Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0835d31e4fa07570d750fdeb59993c73fbced70993fda78c242965a17b98711

Tx prefix hash: 6d85c28d3fe31d59d101e34f36c2b85a023cea5a737d7c4238d38b35da91209f
Tx public key: a8f5aec55059be9ca7a5f97adf36c5c71563c12f442753bf812eeb62d2dc80b2
Timestamp: 1739131911 Timestamp [UCT]: 2025-02-09 20:11:51 Age [y:d:h:m:s]: 00:356:15:01:06
Block: 1215733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252554 RingCT/type: yes/0
Extra: 01a8f5aec55059be9ca7a5f97adf36c5c71563c12f442753bf812eeb62d2dc80b2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbde6d3351835321d6453331699b8dd163becaddc4d6b97dae0f206e76623ff4 0.600000000000 1702532 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": 1215743, "vin": [ { "gen": { "height": 1215733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbde6d3351835321d6453331699b8dd163becaddc4d6b97dae0f206e76623ff4" } } ], "extra": [ 1, 168, 245, 174, 197, 80, 89, 190, 156, 167, 165, 249, 122, 223, 54, 197, 199, 21, 99, 193, 47, 68, 39, 83, 191, 129, 46, 235, 98, 210, 220, 128, 178, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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