Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eedc8a68aa340d2898c9e05f8476a7bfe951596a0d3b935aa108f498e87b25a2

Tx prefix hash: 0f6852bbd118d9e42c22604e0b7ca5e5145b80317f95399c42d4e34fe4f26c9b
Tx public key: d8821e244b5b367360ab56326511bceb3c9df8e7440eab7b108d398d706420d1
Timestamp: 1745416844 Timestamp [UCT]: 2025-04-23 14:00:44 Age [y:d:h:m:s]: 00:018:11:02:35
Block: 1267758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13202 RingCT/type: yes/0
Extra: 01d8821e244b5b367360ab56326511bceb3c9df8e7440eab7b108d398d706420d102110000000edbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f66980df1a0001a33f40cfae158522991f98d6b311e2e127a8cdc87947e542b 0.600000000000 1754987 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": 1267768, "vin": [ { "gen": { "height": 1267758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f66980df1a0001a33f40cfae158522991f98d6b311e2e127a8cdc87947e542b" } } ], "extra": [ 1, 216, 130, 30, 36, 75, 91, 54, 115, 96, 171, 86, 50, 101, 17, 188, 235, 60, 157, 248, 231, 68, 14, 171, 123, 16, 141, 57, 141, 112, 100, 32, 209, 2, 17, 0, 0, 0, 14, 219, 181, 113, 193, 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