Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a865e87c963c582bc164f5f09b76e042f3a0e1fc8b68883d9af7c1c9bb33e16

Tx prefix hash: be151e584b8abcf62b5c5c957b768cdc547f044e9ae845e7cc4c3c582e9a10c2
Tx public key: 50a6662f70fe89c256c749b0caba8c70eb5a0d49fa1750667f39e383b02d54af
Timestamp: 1736206896 Timestamp [UCT]: 2025-01-06 23:41:36 Age [y:d:h:m:s]: 00:070:19:28:37
Block: 1191776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50409 RingCT/type: yes/0
Extra: 0150a6662f70fe89c256c749b0caba8c70eb5a0d49fa1750667f39e383b02d54af02110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edfcb6fe33bb08db57cc15404a835b22bf6b38fb3d4d2932d701ad6a795adcf0 0.600000000000 1678317 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": 1191786, "vin": [ { "gen": { "height": 1191776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edfcb6fe33bb08db57cc15404a835b22bf6b38fb3d4d2932d701ad6a795adcf0" } } ], "extra": [ 1, 80, 166, 102, 47, 112, 254, 137, 194, 86, 199, 73, 176, 202, 186, 140, 112, 235, 90, 13, 73, 250, 23, 80, 102, 127, 57, 227, 131, 176, 45, 84, 175, 2, 17, 0, 0, 0, 14, 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