Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eae6014b74d8920d8afb0389d35f1885b9349a5a8d20f7bd794d398639761b4

Tx prefix hash: 65a0757e88ed816c340da3a1a51e22f8e70aa748d37a0917a80e7f591d8b35f5
Tx public key: 6b817246ad593f8d547702ed7b114670598f3621841c68103618c1aec1ed0e6f
Timestamp: 1724609803 Timestamp [UCT]: 2024-08-25 18:16:43 Age [y:d:h:m:s]: 00:224:12:45:09
Block: 1095784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160319 RingCT/type: yes/0
Extra: 016b817246ad593f8d547702ed7b114670598f3621841c68103618c1aec1ed0e6f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd742f9da1546c4eac5435b71158e3021e4dbeced86bdda4bc874752b6d787ea 0.600000000000 1570967 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": 1095794, "vin": [ { "gen": { "height": 1095784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd742f9da1546c4eac5435b71158e3021e4dbeced86bdda4bc874752b6d787ea" } } ], "extra": [ 1, 107, 129, 114, 70, 173, 89, 63, 141, 84, 119, 2, 237, 123, 17, 70, 112, 89, 143, 54, 33, 132, 28, 104, 16, 54, 24, 193, 174, 193, 237, 14, 111, 2, 17, 0, 0, 0, 5, 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