Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00ce2970ab4b3d5d16b7a6e4fe6045018b28dd9f171f4ba6451a3bd72db41d25

Tx prefix hash: 37acab485421ee19870a8f14234617f6528b11af0442a22e0ba53a1dfdcc18fc
Tx public key: bc342afcc7b389d910f3cb2ac9750635eb36f4f1a3c2e0016570f24da384f108
Timestamp: 1700601995 Timestamp [UCT]: 2023-11-21 21:26:35 Age [y:d:h:m:s]: 01:143:06:03:55
Block: 896728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363561 RingCT/type: yes/0
Extra: 01bc342afcc7b389d910f3cb2ac9750635eb36f4f1a3c2e0016570f24da384f1080211000000024b8f5122000000000000000000

1 output(s) for total of 0.655794658000 dcy

stealth address amount amount idx
00: 737fca0d5ae4ba4dc54ac2a12c735cb3f0eda59e3aa4ddd4851a93aed82bcc37 0.655794658000 1353069 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": 896738, "vin": [ { "gen": { "height": 896728 } } ], "vout": [ { "amount": 655794658, "target": { "key": "737fca0d5ae4ba4dc54ac2a12c735cb3f0eda59e3aa4ddd4851a93aed82bcc37" } } ], "extra": [ 1, 188, 52, 42, 252, 199, 179, 137, 217, 16, 243, 203, 42, 201, 117, 6, 53, 235, 54, 244, 241, 163, 194, 224, 1, 101, 112, 242, 77, 163, 132, 241, 8, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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