Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f7e30ba2e4468beb5b358cec617d014135195de08c9a09a7b3862855276bff

Tx prefix hash: 1432619a201d34b7bcf62446d81b0a9b377a813b8f7fead3288c49b4909ce0c8
Tx public key: f388c602311ab1b586f74034fbaabe76d5a63600ae62a500008a8a1f0f650f02
Timestamp: 1729456549 Timestamp [UCT]: 2024-10-20 20:35:49 Age [y:d:h:m:s]: 01:014:12:45:37
Block: 1135935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268762 RingCT/type: yes/0
Extra: 01f388c602311ab1b586f74034fbaabe76d5a63600ae62a500008a8a1f0f650f02021100000002aa787773000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2e357ec3f64fb75c273fdda8cf355eef44e623448a4d7dbf823f8aa0aa6b7c8 0.600000000000 1619276 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": 1135945, "vin": [ { "gen": { "height": 1135935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2e357ec3f64fb75c273fdda8cf355eef44e623448a4d7dbf823f8aa0aa6b7c8" } } ], "extra": [ 1, 243, 136, 198, 2, 49, 26, 177, 181, 134, 247, 64, 52, 251, 170, 190, 118, 213, 166, 54, 0, 174, 98, 165, 0, 0, 138, 138, 31, 15, 101, 15, 2, 2, 17, 0, 0, 0, 2, 170, 120, 119, 115, 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