Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b57fe245ae3cc3d6b69ed1a79a1d1f0e453254d8dd12295cd9d7437ab6afc462

Tx prefix hash: 81370b8f4d62503cb43038732a4543eaee150291ab6d18dd829165eda004eb12
Tx public key: 81025104e89707282f1a063c23d4620d584ad749459a830b824a8b48f494bbbe
Timestamp: 1726487783 Timestamp [UCT]: 2024-09-16 11:56:23 Age [y:d:h:m:s]: 00:113:18:47:02
Block: 1111342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81361 RingCT/type: yes/0
Extra: 0181025104e89707282f1a063c23d4620d584ad749459a830b824a8b48f494bbbe02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0f28e4c9c5f3c61d01df937a1260e93da8fe052d7ce571c8d8818b0df6f0de0 0.600000000000 1590265 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": 1111352, "vin": [ { "gen": { "height": 1111342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0f28e4c9c5f3c61d01df937a1260e93da8fe052d7ce571c8d8818b0df6f0de0" } } ], "extra": [ 1, 129, 2, 81, 4, 232, 151, 7, 40, 47, 26, 6, 60, 35, 212, 98, 13, 88, 74, 215, 73, 69, 154, 131, 11, 130, 74, 139, 72, 244, 148, 187, 190, 2, 17, 0, 0, 0, 11, 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