Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41bcceaa0788b0bb5fc54ca869e51e9f3d0bfc39afa5d2be0397ef6db2023b5c

Tx prefix hash: 4964cb04671be8d260917514d0123fab5bf5893897b57e60f2e2983c2ca61fb8
Tx public key: 968fc18fc882bde6530a65ac2a80b3ac228c813381c571318fdfcf9680aa0646
Timestamp: 1698674982 Timestamp [UCT]: 2023-10-30 14:09:42 Age [y:d:h:m:s]: 01:138:22:00:35
Block: 880980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360284 RingCT/type: yes/0
Extra: 01968fc18fc882bde6530a65ac2a80b3ac228c813381c571318fdfcf9680aa064602110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.739515973000 dcy

stealth address amount amount idx
00: 89ef9adbb78bdb7ed0082992f0438f8e347a423254f4d5ccf4e1e3e0e76d8085 0.739515973000 1336550 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": 880990, "vin": [ { "gen": { "height": 880980 } } ], "vout": [ { "amount": 739515973, "target": { "key": "89ef9adbb78bdb7ed0082992f0438f8e347a423254f4d5ccf4e1e3e0e76d8085" } } ], "extra": [ 1, 150, 143, 193, 143, 200, 130, 189, 230, 83, 10, 101, 172, 42, 128, 179, 172, 34, 140, 129, 51, 129, 197, 113, 49, 143, 223, 207, 150, 128, 170, 6, 70, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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