Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebafe5ed8f612fa312de91c36d233f76d51382b5613c381a644a2e4a0fdb8ef2

Tx prefix hash: 0780809c1e19b616e3ee30a6034b1ef405d15bcc7f7f4d036ae350c090675a60
Tx public key: 5e3f3173e463d4731d51ac859e9affa07906eac139814c3b4575441abf47cef8
Timestamp: 1727524287 Timestamp [UCT]: 2024-09-28 11:51:27 Age [y:d:h:m:s]: 00:116:18:57:42
Block: 1119941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83460 RingCT/type: yes/0
Extra: 015e3f3173e463d4731d51ac859e9affa07906eac139814c3b4575441abf47cef8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1adaa72695dfe9cb156da853a843f30f1acbdbcd343d1f119916d9ee106dabe 0.600000000000 1601680 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": 1119951, "vin": [ { "gen": { "height": 1119941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1adaa72695dfe9cb156da853a843f30f1acbdbcd343d1f119916d9ee106dabe" } } ], "extra": [ 1, 94, 63, 49, 115, 228, 99, 212, 115, 29, 81, 172, 133, 158, 154, 255, 160, 121, 6, 234, 193, 57, 129, 76, 59, 69, 117, 68, 26, 191, 71, 206, 248, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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