Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 731a8afcfa0ddf56f30471f73940b05a99696addc8051133a7a2c082c32a3bb9

Tx prefix hash: ba8c9cd0bc7f639bd974f1e958069278361d9b9d178ab45d5c4b0bf1a851a76b
Tx public key: be215456d7cbdbeb23d29c3926f71e7778d2d6d0be9eca5064f80af55bc9df8d
Timestamp: 1745762488 Timestamp [UCT]: 2025-04-27 14:01:28 Age [y:d:h:m:s]: 00:256:05:49:41
Block: 1270633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180923 RingCT/type: yes/0
Extra: 01be215456d7cbdbeb23d29c3926f71e7778d2d6d0be9eca5064f80af55bc9df8d0211000000139f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf43059ed21355cf9e8d28667050418e902dcd4fa233b117bc93f09733d40583 0.600000000000 1757876 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": 1270643, "vin": [ { "gen": { "height": 1270633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf43059ed21355cf9e8d28667050418e902dcd4fa233b117bc93f09733d40583" } } ], "extra": [ 1, 190, 33, 84, 86, 215, 203, 219, 235, 35, 210, 156, 57, 38, 247, 30, 119, 120, 210, 214, 208, 190, 158, 202, 80, 100, 248, 10, 245, 91, 201, 223, 141, 2, 17, 0, 0, 0, 19, 159, 159, 230, 140, 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