Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87050b00da57dcbcab7d6c21e3afd79a046b09542874967383f52e6e26488b1c

Tx prefix hash: 1a32cc1d1ca4048956fd139dde9fcf28a689a2646835018518c39bc9e069180a
Tx public key: 7ce6e39e6e667b0d9aec61884ecd44dd7f7747895aaed2ac22a0d24b356aeb1f
Timestamp: 1749697408 Timestamp [UCT]: 2025-06-12 03:03:28 Age [y:d:h:m:s]: 00:151:04:28:29
Block: 1303164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105772 RingCT/type: yes/0
Extra: 017ce6e39e6e667b0d9aec61884ecd44dd7f7747895aaed2ac22a0d24b356aeb1f02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f37ec3f53e581bb51851fd6a8a6f6d5e169e7c30dd628ffe1c8f884d33de9e03 0.600000000000 1790739 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": 1303174, "vin": [ { "gen": { "height": 1303164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f37ec3f53e581bb51851fd6a8a6f6d5e169e7c30dd628ffe1c8f884d33de9e03" } } ], "extra": [ 1, 124, 230, 227, 158, 110, 102, 123, 13, 154, 236, 97, 136, 78, 205, 68, 221, 127, 119, 71, 137, 90, 174, 210, 172, 34, 160, 210, 75, 53, 106, 235, 31, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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