Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe6da41be80c0b96c68484161bc9efb666fd5e87b60941b8a4d38453d5af692d

Tx prefix hash: 48f38eb83146711108f3058d7088d69e8360be5e9714c9a5a931bdf4f9d4cabf
Tx public key: dd89bfae5e18fe7ad321c4df4b6cb0ec139f4f3d633570846558f58e39e1c561
Timestamp: 1724385647 Timestamp [UCT]: 2024-08-23 04:00:47 Age [y:d:h:m:s]: 00:266:07:05:24
Block: 1093929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190190 RingCT/type: yes/0
Extra: 01dd89bfae5e18fe7ad321c4df4b6cb0ec139f4f3d633570846558f58e39e1c561021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7315cf20f055af62ad7fef729c78190c2547adee2a15e37b079956f0f54f231 0.600000000000 1568970 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": 1093939, "vin": [ { "gen": { "height": 1093929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7315cf20f055af62ad7fef729c78190c2547adee2a15e37b079956f0f54f231" } } ], "extra": [ 1, 221, 137, 191, 174, 94, 24, 254, 122, 211, 33, 196, 223, 75, 108, 176, 236, 19, 159, 79, 61, 99, 53, 112, 132, 101, 88, 245, 142, 57, 225, 197, 97, 2, 17, 0, 0, 0, 7, 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