Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c776abe5adb05c778463dc4bbc765c324aa5d9eb478295596f8d22a75538e55f

Tx prefix hash: 7d84f1665e3d5cb6243bdcd0672c432f9792cdefa7810f200f0a2a66459bef67
Tx public key: 1fdc39516c3d96bff5ddcbabfb6a5f7d0e1e18030a4e4572f6b3d8a4b9b0beb5
Timestamp: 1729739534 Timestamp [UCT]: 2024-10-24 03:12:14 Age [y:d:h:m:s]: 01:026:05:53:43
Block: 1138269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277145 RingCT/type: yes/0
Extra: 011fdc39516c3d96bff5ddcbabfb6a5f7d0e1e18030a4e4572f6b3d8a4b9b0beb50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31c0f3517a0506ce27cd8cdd1b2bec173479540416987cbf444ea56ebca330b9 0.600000000000 1621896 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": 1138279, "vin": [ { "gen": { "height": 1138269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31c0f3517a0506ce27cd8cdd1b2bec173479540416987cbf444ea56ebca330b9" } } ], "extra": [ 1, 31, 220, 57, 81, 108, 61, 150, 191, 245, 221, 203, 171, 251, 106, 95, 125, 14, 30, 24, 3, 10, 78, 69, 114, 246, 179, 216, 164, 185, 176, 190, 181, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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