Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d78f9c77e932e8a3c4831d8ce52a2bac1798ba7db597db7d35ab8fd6bd73e6ab

Tx prefix hash: ef0d20e07045229a996508bb0ed55ce93eb0596460b473d345f419c30e64e857
Tx public key: b876b00b34d2d8f290a676f1342f7f42e4c276bdf0d49f3165f3584df34fffee
Timestamp: 1752921163 Timestamp [UCT]: 2025-07-19 10:32:43 Age [y:d:h:m:s]: 00:121:16:34:38
Block: 1328764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85768 RingCT/type: yes/0
Extra: 01b876b00b34d2d8f290a676f1342f7f42e4c276bdf0d49f3165f3584df34fffee02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc605075d1e766dd9c3df7a464107c697625f8870569f0c3b170021389dec9ee 0.600000000000 1816533 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": 1328774, "vin": [ { "gen": { "height": 1328764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc605075d1e766dd9c3df7a464107c697625f8870569f0c3b170021389dec9ee" } } ], "extra": [ 1, 184, 118, 176, 11, 52, 210, 216, 242, 144, 166, 118, 241, 52, 47, 127, 66, 228, 194, 118, 189, 240, 212, 159, 49, 101, 243, 88, 77, 243, 79, 255, 238, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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