Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2365777c1e13687b8d195ad6364b83544d3f07f3a39184904944a2911f682f9

Tx prefix hash: 6e51fc0fbe2c0a3488d5baeaf26ae7dee90d9b3fcf0c0cbeb1ef4665cda17fb9
Tx public key: fec8ebd4ea76fc9f74c4ca5f389028dbdd394ff0a425c58166371ce7afbe7b03
Timestamp: 1720998840 Timestamp [UCT]: 2024-07-14 23:14:00 Age [y:d:h:m:s]: 00:273:17:10:38
Block: 1065852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195543 RingCT/type: yes/0
Extra: 01fec8ebd4ea76fc9f74c4ca5f389028dbdd394ff0a425c58166371ce7afbe7b0302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 824419a5f1628833e99dbe5a2e3afde2eff754878272b3a7ffdad9d9c3f74d8e 0.600000000000 1536417 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": 1065862, "vin": [ { "gen": { "height": 1065852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "824419a5f1628833e99dbe5a2e3afde2eff754878272b3a7ffdad9d9c3f74d8e" } } ], "extra": [ 1, 254, 200, 235, 212, 234, 118, 252, 159, 116, 196, 202, 95, 56, 144, 40, 219, 221, 57, 79, 240, 164, 37, 197, 129, 102, 55, 28, 231, 175, 190, 123, 3, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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