Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f3f0ee2c12d3ec3fe148fd17171cc6cc4b912517da80fc287218c573f6fdb2

Tx prefix hash: 3f01fd90c4268e7e6303cdd30d6491bf4f93222d3cfb1217ed0eb8bb121d026d
Tx public key: 206c12d21dd957d27092de2b9020a4b14e864822864c5cc3332a15de8bbfcd89
Timestamp: 1746867664 Timestamp [UCT]: 2025-05-10 09:01:04 Age [y:d:h:m:s]: 00:263:10:38:41
Block: 1279775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185905 RingCT/type: yes/0
Extra: 01206c12d21dd957d27092de2b9020a4b14e864822864c5cc3332a15de8bbfcd890211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a03195bcca2b1ba4f91d1fbccfc11bdba224a203f0f81a9b5fa2ae9f6e7a5a4 0.600000000000 1767156 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": 1279785, "vin": [ { "gen": { "height": 1279775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a03195bcca2b1ba4f91d1fbccfc11bdba224a203f0f81a9b5fa2ae9f6e7a5a4" } } ], "extra": [ 1, 32, 108, 18, 210, 29, 217, 87, 210, 112, 146, 222, 43, 144, 32, 164, 177, 78, 134, 72, 34, 134, 76, 92, 195, 51, 42, 21, 222, 139, 191, 205, 137, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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