Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d93c0454577da1ef276f066d14ce5c8ef3173868ecfb8b57bd8dab5c49424e5

Tx prefix hash: 362708c9a1465fbc73dcfc770faed377ed7e7079e2e51b60a2d6cd1f1d19b913
Tx public key: 0f233c48ceab3da4a97e6e4c046ed6eceacee43a2ef96bad6997ea4897dbb02a
Timestamp: 1700962001 Timestamp [UCT]: 2023-11-26 01:26:41 Age [y:d:h:m:s]: 01:129:06:49:17
Block: 899715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353561 RingCT/type: yes/0
Extra: 010f233c48ceab3da4a97e6e4c046ed6eceacee43a2ef96bad6997ea4897dbb02a02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.641018700000 dcy

stealth address amount amount idx
00: c6888087aed46bf708938329a784a57e4d3b26c5f560d5537e6d6572a2683008 0.641018700000 1356178 of 0

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": 899725, "vin": [ { "gen": { "height": 899715 } } ], "vout": [ { "amount": 641018700, "target": { "key": "c6888087aed46bf708938329a784a57e4d3b26c5f560d5537e6d6572a2683008" } } ], "extra": [ 1, 15, 35, 60, 72, 206, 171, 61, 164, 169, 126, 110, 76, 4, 110, 214, 236, 234, 206, 228, 58, 46, 249, 107, 173, 105, 151, 234, 72, 151, 219, 176, 42, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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