Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8faf2e2eb591719b66e2baba5c33a819a025e817426c35401a2cbc845634376e

Tx prefix hash: 39eb1d50dc1372c938d334e4931c8eee170f22d5e1873b27497f9d92d14432ae
Tx public key: 1bfc6b64c4de99110ac1569246eb42bbaf3c3858bfa36f017b8b94c0b8eab3c8
Timestamp: 1682240920 Timestamp [UCT]: 2023-04-23 09:08:40 Age [y:d:h:m:s]: 01:357:05:09:01
Block: 744756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516580 RingCT/type: yes/0
Extra: 011bfc6b64c4de99110ac1569246eb42bbaf3c3858bfa36f017b8b94c0b8eab3c802110000000233af99f4000000000000000000

1 output(s) for total of 2.090829284000 dcy

stealth address amount amount idx
00: 12d768b920a1dcee50b2d02b0a349e1c471cdbea3c4fb35c4fbc3bd807ded6c7 2.090829284000 1192131 of 0

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": 744766, "vin": [ { "gen": { "height": 744756 } } ], "vout": [ { "amount": 2090829284, "target": { "key": "12d768b920a1dcee50b2d02b0a349e1c471cdbea3c4fb35c4fbc3bd807ded6c7" } } ], "extra": [ 1, 27, 252, 107, 100, 196, 222, 153, 17, 10, 193, 86, 146, 70, 235, 66, 187, 175, 60, 56, 88, 191, 163, 111, 1, 123, 139, 148, 192, 184, 234, 179, 200, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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