Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6136d8378c78da5604b698d4efde7cb61ade4d08990e26967257dfadc2f3a466

Tx prefix hash: f439be29796e1055daf02c477cc29fd23806a5ed293096aa2b2a2ce09787f6ae
Tx public key: 10f828f31bdcab132ec0ad0444bde7f640e21f6a64546e1fb347091b36926cdd
Timestamp: 1673001403 Timestamp [UCT]: 2023-01-06 10:36:43 Age [y:d:h:m:s]: 01:330:23:15:24
Block: 668775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497570 RingCT/type: yes/0
Extra: 0110f828f31bdcab132ec0ad0444bde7f640e21f6a64546e1fb347091b36926cdd02110000000352542ceb000000000000000000

1 output(s) for total of 3.733109787000 dcy

stealth address amount amount idx
00: 3cc90357d32dd3e5e97e290c6b63d79b7f6d52d9fb8c46002ad5b2af02259d8c 3.733109787000 1110042 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": 668785, "vin": [ { "gen": { "height": 668775 } } ], "vout": [ { "amount": 3733109787, "target": { "key": "3cc90357d32dd3e5e97e290c6b63d79b7f6d52d9fb8c46002ad5b2af02259d8c" } } ], "extra": [ 1, 16, 248, 40, 243, 27, 220, 171, 19, 46, 192, 173, 4, 68, 189, 231, 246, 64, 226, 31, 106, 100, 84, 110, 31, 179, 71, 9, 27, 54, 146, 108, 221, 2, 17, 0, 0, 0, 3, 82, 84, 44, 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