Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3f7a63812911aca2e1e5286c2e33cf703e4baf461b74bcb4a840e7ef461c498

Tx prefix hash: 29d4553994ea3057919f9b2eaed02fde0f0f1952132c892855c914d0f87108f5
Tx public key: 036ee0e4720ad4e382ad95969f9f18bd902b628edfcca19137a4cc02ae57b5a6
Timestamp: 1729677270 Timestamp [UCT]: 2024-10-23 09:54:30 Age [y:d:h:m:s]: 00:066:00:25:27
Block: 1137754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47194 RingCT/type: yes/0
Extra: 01036ee0e4720ad4e382ad95969f9f18bd902b628edfcca19137a4cc02ae57b5a60211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec4eaefdfc7348ee659ff5827cced94d8c55c2418904e03f2d95873ff0a55df3 0.600000000000 1621305 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": 1137764, "vin": [ { "gen": { "height": 1137754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec4eaefdfc7348ee659ff5827cced94d8c55c2418904e03f2d95873ff0a55df3" } } ], "extra": [ 1, 3, 110, 224, 228, 114, 10, 212, 227, 130, 173, 149, 150, 159, 159, 24, 189, 144, 43, 98, 142, 223, 204, 161, 145, 55, 164, 204, 2, 174, 87, 181, 166, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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