Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3ae7da98c3f90b4665a5677c69a9d428c5221ad1d7238ec9123c69eb48898bd

Tx prefix hash: 5d39c42f7902680a9dfc19a7505d6cd9f15b0a23bbf53a76729f2629cad3f8c5
Tx public key: c250c2ab4a354fcdfe1001a31f5d79f481200478266fe584dd5dc574287b30b9
Timestamp: 1730474865 Timestamp [UCT]: 2024-11-01 15:27:45 Age [y:d:h:m:s]: 00:161:05:47:28
Block: 1144312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115086 RingCT/type: yes/0
Extra: 01c250c2ab4a354fcdfe1001a31f5d79f481200478266fe584dd5dc574287b30b9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b2fd6806a471b2c20c21877ca62ab86323a7ff3b710b0a1f9ea1ebaf8572475 0.600000000000 1628487 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": 1144322, "vin": [ { "gen": { "height": 1144312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b2fd6806a471b2c20c21877ca62ab86323a7ff3b710b0a1f9ea1ebaf8572475" } } ], "extra": [ 1, 194, 80, 194, 171, 74, 53, 79, 205, 254, 16, 1, 163, 31, 93, 121, 244, 129, 32, 4, 120, 38, 111, 229, 132, 221, 93, 197, 116, 40, 123, 48, 185, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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