Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f1d20e343b1b4b006d679d5d13a1eb359e33882a401c4ae9247f296a89005c

Tx prefix hash: 8b5766c85cbe72292e75e7f869e9821dbbdcd90218533e5c49e1d1ca341b5504
Tx public key: 1029ac2da52734e3c62f5d120c063119bae19dce83a4d86868e9183e3344e35f
Timestamp: 1732105306 Timestamp [UCT]: 2024-11-20 12:21:46 Age [y:d:h:m:s]: 00:141:11:19:37
Block: 1157811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100933 RingCT/type: yes/0
Extra: 011029ac2da52734e3c62f5d120c063119bae19dce83a4d86868e9183e3344e35f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39854915c2c120cbbaaa9c4e513ca951c33c75ac1ef9584f1a5e5f7a8e6052bb 0.600000000000 1643434 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": 1157821, "vin": [ { "gen": { "height": 1157811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39854915c2c120cbbaaa9c4e513ca951c33c75ac1ef9584f1a5e5f7a8e6052bb" } } ], "extra": [ 1, 16, 41, 172, 45, 165, 39, 52, 227, 198, 47, 93, 18, 12, 6, 49, 25, 186, 225, 157, 206, 131, 164, 216, 104, 104, 233, 24, 62, 51, 68, 227, 95, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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