Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e04f118dcf6c45fbb82f76f1139cdb7dcfa4f6242c5fbce1312977b8d9af70bc

Tx prefix hash: cb00d64671d653a202099d1e8ba4325d9f2eb22fffcba2addb08bb74845f3e04
Tx public key: 29157deb998c0333f7e26d1b6ca533dbf3f84b2b90a6be79a338f8d5e18d780a
Timestamp: 1728387327 Timestamp [UCT]: 2024-10-08 11:35:27 Age [y:d:h:m:s]: 00:203:17:44:11
Block: 1127090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145422 RingCT/type: yes/0
Extra: 0129157deb998c0333f7e26d1b6ca533dbf3f84b2b90a6be79a338f8d5e18d780a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5e653532067ef5ecd2464fb506047d30d85473e13ea9bbd524e12deba17cddf 0.600000000000 1609889 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": 1127100, "vin": [ { "gen": { "height": 1127090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5e653532067ef5ecd2464fb506047d30d85473e13ea9bbd524e12deba17cddf" } } ], "extra": [ 1, 41, 21, 125, 235, 153, 140, 3, 51, 247, 226, 109, 27, 108, 165, 51, 219, 243, 248, 75, 43, 144, 166, 190, 121, 163, 56, 248, 213, 225, 141, 120, 10, 2, 17, 0, 0, 0, 3, 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